1. fix remote does not respond go away

In the current implementation, if the other party does not respond to go away, yamux will wait forever, causing a possible fd attack. Although this is a poorly maintained attack method, during the attack, it must respond to ping/pong messages, otherwise, it will be closed. We cannot be sure whether the remote implementation is fully compliant with the specification. At this time, there must be a shutdown strategy, which is to set a timeout time. When the remote timeout does not respond, the connection will be closed by itself.

Since yamux needs to be runtime independent, the only thing that can be done here is to instantly replace the ping timer, whether it exists or not, at the same time, due to the inconsistency of timer implementation, it is necessary to force the poll once and register it to the corresponding driver, otherwise, it may cause the problem of not being able to wake up(like this ci error)

2. fix drop with local close should send event

For stream closing, the normal closing process is:

local -- fin ---> remote
remote -- fin ---> local, and remove resources registered in the session
local informs to clean up resources after receiving fin

This is a closing process of a streaming connection with a semi-closed feature

The local close state only performed the fin operation sent to the remote and did not perform notification cleanup